Techniques For Reducing Messaging Requirements In Wireless Power Delivery Environments

ABSTRACT

Techniques are described for retention of known data within a wireless power transmission system, or within a cloud-based processing system. In order to perform scheduling procedures for determining which device to power, it is necessary to collect data regarding a device, e.g., the battery type, power usage, device model, present charge level and amount of power delivered per power cycle. A wireless power receiver client typically needs to collect or infer the information from the device and then provide the information directly to the charger via a messaging protocol. In existing wireless power transmission systems, information is re-transmitted to the wireless power transmission system every time the receiver engages or reengages the system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/176,608 titled “TECHNIQUES FOR REDUCING MESSAGING REQUIREMENTS INWIRELESS POWER DELIVERY ENVIRONMENTS” filed on Jun. 8, 2016; whichclaims priority to and benefit from U.S. Provisional Patent ApplicationNo. 62/172,752 titled “SYSTEMS AND METHODS FOR IMPROVED WIRELESS POWERTRANSFERS” filed on Jun. 8, 2015, both of which are expresslyincorporated by reference herein.

TECHNICAL FIELD

The technology described herein relates generally to the field ofwireless power transmission and, more specifically, to techniques forreducing messaging requirements in wireless power delivery environments.

BACKGROUND

Many electronic devices are powered by batteries. Rechargeable batteriesare often used to avoid the cost of replacing conventional dry-cellbatteries and to conserve precious resources. However, rechargingbatteries with conventional rechargeable battery chargers requiresaccess to an alternating current (AC) power outlet, which is sometimesnot available or not convenient. It would, therefore, be desirable toderive power for electronics wirelessly.

Accordingly, a need exists for technology that overcomes the problemdemonstrated above, as well as one that provides additional benefits.The examples provided herein of some prior or related systems and theirassociated limitations are intended to be illustrative and notexclusive. Other limitations of existing or prior systems will becomeapparent to those of skill in the art upon reading the followingDetailed Description.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more embodiments of the present invention are illustrated by wayof example and not limitation in the figures of the accompanyingdrawings, in which like references indicate similar elements.

FIG. 1 depicts a block diagram including an example wireless powerdelivery environment illustrating wireless power delivery from one ormore wireless power transmission systems to various wireless deviceswithin the wireless power delivery environment in accordance with someembodiments.

FIG. 2 depicts a sequence diagram illustrating example operationsbetween a wireless power transmission system and a wireless receiverclient for commencing wireless power delivery in accordance with someembodiments.

FIG. 3 depicts a block diagram illustrating example components of awireless power transmission system in accordance with some embodiments.

FIG. 4 depicts a block diagram illustrating example components of awireless power receiver client in accordance with some embodiments.

FIGS. 5A and 5B depict diagrams illustrating an example multipathwireless power delivery environment in accordance with some embodiments.

FIG. 6 depicts a diagram illustrating an example wireless power deliveryenvironment in accordance with some embodiments.

FIG. 7 depicts a sequence diagram illustrating example operations forreducing messaging in a wireless power delivery environment inaccordance with some embodiments.

FIG. 8 depicts a flow diagram illustrating an example process forreducing unnecessary messaging in a wireless power delivery environmentin accordance with some embodiments.

FIG. 9 depicts an example device registry table in accordance with someembodiments.

FIG. 10 depicts a block diagram illustrating example components of arepresentative mobile device or tablet computer with one or morewireless power receiver clients in the form of a mobile (or smart) phoneor tablet computer device in accordance with some embodiments.

FIG. 11 depicts a diagrammatic representation of a machine, in theexample form, of a computer system within which a set of instructions,for causing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

DETAILED DESCRIPTION

Techniques are described for retention of known data within a wirelesspower transmission system, or within a cloud-based processing system. Inorder to perform scheduling procedures for determining which devices toprovide power, it is necessary to collect data regarding a device, e.g.,the battery type, power usage, device model, present charge level and/oramount of power delivered per power cycle. A wireless power receiverclient typically needs to collect or infer the information from thedevice and then provide the information directly to the charger via amessaging protocol. In existing wireless power transmission systems,information is re-transmitted to the wireless power transmission systemevery time the receiver engages or reengages the system.

The following description and drawings are illustrative and are not tobe construed as limiting. Numerous specific details are described toprovide a thorough understanding of the disclosure. However, in certaininstances, well-known or conventional details are not described in orderto avoid obscuring the description. References to one or an embodimentin the present disclosure can be, but not necessarily are, references tothe same embodiment; and, such references mean at least one of theembodiments.

Reference in this specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment, nor are separate or alternative embodimentsmutually exclusive of other embodiments. Moreover, various features aredescribed which may be exhibited by some embodiments and not by others.Similarly, various requirements are described which may be requirementsfor some embodiments but no other embodiments.

The terms used in this specification generally have their ordinarymeanings in the art, within the context of the disclosure, and in thespecific context where each term is used. Certain terms that are used todescribe the disclosure are discussed below, or elsewhere in thespecification, to provide additional guidance to the practitionerregarding the description of the disclosure. For convenience, certainterms may be highlighted, for example using italics and/or quotationmarks. The use of highlighting has no influence on the scope and meaningof a term; the scope and meaning of a term is the same, in the samecontext, whether or not it is highlighted. It will be appreciated thatsame thing can be said in more than one way.

Consequently, alternative language and synonyms may be used for any oneor more of the terms discussed herein, nor is any special significanceto be placed upon whether or not a term is elaborated or discussedherein. Synonyms for certain terms are provided. A recital of one ormore synonyms does not exclude the use of other synonyms. The use ofexamples anywhere in this specification, including examples of any termsdiscussed herein, is illustrative only, and is not intended to furtherlimit the scope and meaning of the disclosure or of any exemplifiedterm. Likewise, the disclosure is not limited to various embodimentsgiven in this specification.

Without intent to further limit the scope of the disclosure, examples ofinstruments, apparatus, methods and their related results according tothe embodiments of the present disclosure are given below. Note thattitles or subtitles may be used in the examples for convenience of areader, which in no way should limit the scope of the disclosure. Unlessotherwise defined, all technical and scientific terms used herein havethe same meaning as commonly understood by one of ordinary skill in theart to which this disclosure pertains. In the case of conflict, thepresent document, including definitions, will control.

I. Wireless Power Transmission System Overview/Architecture

FIG. 1 depicts a block diagram including an example wireless powerdelivery environment 100 illustrating wireless power delivery from oneor more wireless power transmission systems (WPTS) 101 a-n (alsoreferred to as “wireless power delivery systems”, “antenna arraysystems” and “wireless chargers”) to various wireless devices 102 a-nwithin the wireless power delivery environment 100, according to someembodiments. More specifically, FIG. 1 illustrates an example wirelesspower delivery environment 100 in which wireless power and/or data canbe delivered to available wireless devices 102 a-102 n having one ormore wireless power receiver clients 103 a-103 n (also referred toherein as “clients” and “wireless power receivers”). The wireless powerreceiver clients are configured to receive and process wireless powerfrom one or more wireless power transmission systems 101 a-101 n.Components of an example wireless power receiver client 103 are shownand discussed in greater detail with reference to FIG. 4.

As shown in the example of FIG. 1, the wireless devices 102 a-102 ninclude mobile phone devices and a wireless game controller. However,the wireless devices 102 a-102 n can be any device or system that needspower and is capable of receiving wireless power via one or moreintegrated power receiver clients 103 a-103 n. As discussed herein, theone or more integrated power receiver clients receive and process powerfrom one or more wireless power transmission systems 101 a-101 n andprovide the power to the wireless devices 102 a-102 n (or internalbatteries of the wireless devices) for operation thereof.

Each wireless power transmission system 101 can include multipleantennas 104 a-n, e.g., an antenna array including hundreds or thousandsof antennas, which are capable of delivering wireless power to wirelessdevices 102. In some embodiments, the antennas are adaptively-phasedradio frequency (RF) antennas. The wireless power transmission system101 is capable of determining the appropriate phases with which todeliver a coherent power transmission signal to the power receiverclients 103. The array is configured to emit a signal (e.g., continuouswave or pulsed power transmission signal) from multiple antennas at aspecific phase relative to each other. It is appreciated that use of theterm “array” does not necessarily limit the antenna array to anyspecific array structure. That is, the antenna array does not need to bestructured in a specific “array” form or geometry. Furthermore, as usedherein the term “array” or “array system” may be used include relatedand peripheral circuitry for signal generation, reception andtransmission, such as radios, digital logic and modems. In someembodiments, the wireless power transmission system 101 can have anembedded Wi-Fi hub for data communications via one or more antennas ortransceivers.

The wireless devices 102 can include one or more receive power clients103. As illustrated in the example of FIG. 1, power delivery antennas104 a-104 n are shown. The power delivery antennas 104 a are configuredto provide delivery of wireless radio frequency power in the wirelesspower delivery environment. In some embodiments, one or more of thepower delivery antennas 104 a-104 n can alternatively or additionally beconfigured for data communications in addition to or in lieu of wirelesspower delivery. The one or more data communication antennas areconfigured to send data communications to and receive datacommunications from the power receiver clients 103 a-103 n and/or thewireless devices 102 a-102 n. In some embodiments, the datacommunication antennas can communicate via Bluetooth™, Wi-Fi™, ZigBee™,etc. Other data communication protocols are also possible.

Each power receiver client 103 a-103 n includes one or more antennas(not shown) for receiving signals from the wireless power transmissionsystems 101 a-101 n. Likewise, each wireless power transmission system101 a-101 n includes an antenna array having one or more antennas and/orsets of antennas capable of emitting continuous wave or discrete (pulse)signals at specific phases relative to each other. As discussed above,each the wireless power transmission systems 101 a-101 n is capable ofdetermining the appropriate phases for delivering the coherent signalsto the power receiver clients 102 a-102 n. For example, in someembodiments, coherent signals can be determined by computing the complexconjugate of a received beacon (or calibration) signal at each antennaof the array such that the coherent signal is phased for deliveringpower to the particular power receiver client that transmitted thebeacon (or calibration) signal.

Although not illustrated, each component of the environment, e.g.,wireless device, wireless power transmission system, etc., can includecontrol and synchronization mechanisms, e.g., a data communicationsynchronization module. The wireless power transmission systems 101a-101 n can be connected to a power source such as, for example, a poweroutlet or source connecting the wireless power transmission systems to astandard or primary alternating current (AC) power supply in a building.Alternatively, or additionally, one or more of the wireless powertransmission systems 101 a-101 n can be powered by a battery or viaother mechanisms, e.g., solar cells, etc.

The power receiver clients 102 a-102 n and/or the wireless powertransmission systems 101 a-101 n are configured to operate in amultipath wireless power delivery environment. That is, the powerreceiver clients 102 a-102 n and the wireless power transmission systems101 a-101 n are configured to utilize reflective objects 106 such as,for example, walls or other RF reflective obstructions within range totransmit beacon (or calibration) signals and/or receive wireless powerand/or data within the wireless power delivery environment. Thereflective objects 106 can be utilized for multi-directional signalcommunication regardless of whether a blocking object is in the line ofsight between the wireless power transmission system and the powerreceiver client.

As described herein, each wireless device 102 a-102 n can be any systemand/or device, and/or any combination of devices/systems that canestablish a connection with another device, a server and/or othersystems within the example environment 100. In some embodiments, thewireless devices 102 a-102 n include displays or other outputfunctionalities to present data to a user and/or input functionalitiesto receive data from the user. By way of example, a wireless device 102can be, but is not limited to, a video game controller, a serverdesktop, a desktop computer, a computer cluster, a mobile computingdevice such as a notebook, a laptop computer, a handheld computer, amobile phone, a smart phone, a PDA, a Blackberry device, a Treo, and/oran iPhone, etc. By way of example and not limitation, the wirelessdevice 102 can also be any wearable device such as watches, necklaces,rings or even devices embedded on or within the customer. Other examplesof a wireless device 102 include, but are not limited to, safety sensors(e.g., fire or carbon monoxide), electric toothbrushes, electronic doorlock/handles, electric light switch controller, electric shavers, etc.

Although not illustrated in the example of FIG. 1, the wireless powertransmission system 101 and the power receiver clients 103 a-103 n caneach include a data communication module for communication via a datachannel. Alternatively, or additionally, the power receiver clients 103a-103 n can direct the wireless devices 102.1-102.n to communicate withthe wireless power transmission system via existing data communicationsmodules. In some embodiments the beacon signal, which is primarilyreferred to herein as a continuous waveform, can alternatively oradditionally take the form of a modulated signal.

FIG. 2 is a sequence diagram 200 illustrating example operations betweena wireless power delivery system (e.g., WPTS 101) and a wireless powerreceiver client (e.g., wireless power receiver client 103) forestablishing wireless power delivery in a multipath wireless powerdelivery, according to an embodiment. Initially, communication isestablished between the wireless power transmission system 101 and thepower receiver client 103. The initial communication can be, forexample, a data communication link that is established via one or moreantennas 104 of the wireless power transmission system 101. Asdiscussed, in some embodiments, one or more of the antennas 104 a-104 ncan be data antennas, wireless power transmission antennas, ordual-purpose data/power antennas. Various information can be exchangedbetween the wireless power transmission system 101 and the wirelesspower receiver client 103 over this data communication channel. Forexample, wireless power signaling can be time sliced among variousclients in a wireless power delivery environment. In such cases, thewireless power transmission system 101 can send beacon scheduleinformation, e.g., Beacon Beat Schedule (BBS) cycle, power cycleinformation, etc., so that the wireless power receiver client 103 knowswhen to transmit (broadcast) its beacon signals and when to listen forpower, etc.

Continuing with the example of FIG. 2, the wireless power transmissionsystem 101 selects one or more wireless power receiver clients forreceiving power and sends the beacon schedule information to the selectpower receiver clients 103. The wireless power transmission system 101can also send power transmission scheduling information so that thepower receiver client 103 knows when to expect (e.g., a window of time)wireless power from the wireless power transmission system. The powerreceiver client 103 then generates a beacon (or calibration) signal andbroadcasts the beacon during an assigned beacon transmission window (ortime slice) indicated by the beacon schedule information, e.g., BeaconBeat Schedule (BBS) cycle. As discussed herein, the wireless powerreceiver client 103 include one or more antennas (or transceivers) whichhave a radiation and reception pattern in three-dimensional spaceproximate to the wireless device 102 in which the power receiver client103 is embedded.

The wireless power transmission system 101 receives the beacon from thepower receiver client 103 and detects and/or otherwise measures thephase (or direction) from which the beacon signal is received atmultiple antennas. The wireless power transmission system 101 thendelivers wireless power to the power receiver client 103 from themultiple antennas 103 based on the detected or measured phase (ordirection) of the received beacon at each of the corresponding antennas.In some embodiments, the wireless power transmission system 101determines the complex conjugate of the measured phase of the beacon anduses the complex conjugate to determine a transmit phase that configuresthe antennas for delivering and/or otherwise directing wireless power tothe power receiver client 103 via the same path over which the beaconsignal was received from the power receiver client 103.

In some embodiments, the wireless power transmission system 101 includesmany antennas; one or more of which are used to deliver power to thepower receiver client 103. The wireless power transmission system 101can detect and/or otherwise determine or measure phases at which thebeacon signals are received at each antenna. The large number ofantennas may result in different phases of the beacon signal beingreceived at each antenna of the wireless power transmission system 101.As discussed above, the wireless power transmission system 101 candetermine the complex conjugate of the beacon signals received at eachantenna. Using the complex conjugates, one or more antennas may emit asignal that takes into account the effects of the large number ofantennas in the wireless power transmission system 101. In other words,the wireless power transmission system 101 can emit a wireless powertransmission signal from the one or more antennas in such a way as tocreate an aggregate signal from the one or more of the antennas thatapproximately recreates the waveform of the beacon in the oppositedirection. Said another way, the wireless power transmission system 101can deliver wireless RF power to the client device via the same pathsover which the beacon signal is received at the wireless powertransmission system 101. These paths can utilize reflective objects 106within the environment. Additionally, the wireless power transmissionsignals can be simultaneously transmitted from the wireless powertransmission system 101 such that the wireless power transmissionsignals collectively match the antenna radiation and reception patternof the client device in a three-dimensional (3D) space proximate to theclient device.

As shown, the beacon (or calibration) signals can be periodicallytransmitted by power receiver clients 103 within the power deliveryenvironment according to, for example, the BBS, so that the wirelesspower transmission system 101 can maintain knowledge and/or otherwisetrack the location of the power receiver clients 103 in the wirelesspower delivery environment. The process of receiving beacon signals froma wireless power receiver client at the wireless power transmissionsystem and, in turn, responding with wireless power directed to thatparticular client is referred to herein as retrodirective wireless powerdelivery.

Furthermore, as discussed herein, wireless power can be delivered inpower cycles defined by power schedule information. A more detailedexample of the signaling required to commence wireless power delivery isdescribed now with reference to FIG. 3.

FIG. 3 is a block diagram illustrating example components of a wirelesspower transmission system 300, in accordance with an embodiment. Asillustrated in the example of FIG. 3, the wireless charger 300 includesa master bus controller (MBC) board and multiple mezzanine boards thatcollectively comprise the antenna array. The MBC includes control logic310, an external data interface (I/F) 315, an external power interface(I/F) 320, a communication block 330 and proxy 340. The mezzanine (orantenna array boards 350) each include multiple antennas 360 a-360 n.Some or all of the components can be omitted in some embodiments.Additional components are also possible. For example, in someembodiments only one of communication block 330 or proxy 340 may beincluded.

The control logic 310 is configured to provide control and intelligenceto the array components. The control logic 310 may comprise one or moreprocessors, FPGAs, memory units, etc., and direct and control thevarious data and power communications. The communication block 330 candirect data communications on a data carrier frequency, such as the basesignal clock for clock synchronization. The data communications can beBluetooth™, Wi-Fi™, ZigBee™, etc., including combinations or variationsthereof. Likewise, the proxy 340 can communicate with clients via datacommunications as discussed herein. The data communications can be, byway of example and not limitation, Bluetooth™, Wi-Fi™, ZigBee™, etc.Other communication protocols are possible.

In some embodiments, the control logic 310 can also facilitate and/orotherwise enable data aggregation for Internet of Things (IoT) devices.In some embodiments, wireless power receiver clients can access, trackand/or otherwise obtain IoT information about the device in which thewireless power receiver client is embedded and provide that IoTinformation to the wireless power transmission system 300 over a dataconnection. This IoT information can be provided to via an external datainterface 315 to a central or cloud-based system (not shown) where thedata can be aggregated, processed, etc. For example, the central systemcan process the data to identify various trends across geographies,wireless power transmission systems, environments, devices, etc. In someembodiments, the aggregated data and or the trend data can be used toimprove operation of the devices via remote updates, etc. Alternatively,or additionally, in some embodiments, the aggregated data can beprovided to third party data consumers. In this manner, the wirelesspower transmission system acts as a Gateway or Enabler for the IoTs. Byway of example and not limitation, the IoT information can includecapabilities of the device in which the wireless power receiver clientis embedded, usage information of the device, power levels of thedevice, information obtained by the device or the wireless powerreceiver client itself, e.g., via sensors, etc.

The external power interface 320 is configured to receive external powerand provide the power to various components. In some embodiments, theexternal power interface 320 may be configured to receive a standardexternal 24 Volt power supply. In other embodiments, the external powerinterface 320 can be, for example, 120/240 Volt AC mains to an embeddedDC power supply which sources the required 12/24/48 Volt DC to providethe power to various components. Alternatively, the external powerinterface could be a DC supply which sources the required 12/24/48 VoltsDC. Alternative configurations are also possible.

In operation, the master bus controller (MBC), which controls thewireless power transmission system 300, receives power from a powersource and is activated. The MBC then activates the proxy antennaelements on the wireless power transmission system and the proxy antennaelements enter a default “discovery” mode to identify available wirelessreceiver clients within range of the wireless power transmission system.When a client is found, the antenna elements on the wireless powertransmission system power on, enumerate, and (optionally) calibrate.

The MBC then generates beacon transmission scheduling information andpower transmission scheduling information during a scheduling process.The scheduling process includes selection of power receiver clients. Forexample, the MBC can select power receiver clients for powertransmission and generate a Beacon Beat Schedule (BBS) cycle and a PowerSchedule (PS) for the selected wireless power receiver clients. Asdiscussed herein, the power receiver clients can be selected based ontheir corresponding properties and/or requirements.

In some embodiments, the MBC can also identify and/or otherwise selectavailable clients that will have their status queried in the ClientQuery Table (CQT). Clients that are placed in the CQT are those on“standby”, e.g., not receiving a charge. The BBS and PS are calculatedbased on vital information about the clients such as, for example,battery status, current activity/usage, how much longer the client hasuntil it runs out of power, priority in terms of usage, etc.

The Proxy AE broadcasts the BBS to all clients. As discussed herein, theBBS indicates when each client should send a beacon. Likewise, the PSindicates when and to which clients the array should send power to andwhen clients should listen for wireless power. Each client startsbroadcasting its beacon and receiving power from the array per the BBSand PS. The Proxy can concurrently query the Client Query Table to checkthe status of other available clients. In some embodiments, a client canonly exist in the BBS or the CQT (e.g., waitlist), but not in both. Theinformation collected in the previous step continuously and/orperiodically updates the BBS cycle and/or the PS.

FIG. 4 is a block diagram illustrating example components of a wirelesspower receiver client, in accordance with some embodiments. Asillustrated in the example of FIG. 4, the receiver 400 includes controllogic 410, battery 420, an IoT control module 425, communication block430 and associated antenna 470, power meter 440, rectifier 450, acombiner 455, beacon signal generator 460, beacon coding unit 462 and anassociated antenna 480, and switch 465 connecting the rectifier 450 orthe beacon signal generator 460 to one or more associated antennas 490a-n. Some or all of the components can be omitted in some embodiments.For example, in some embodiments, the wireless power receiver clientdoes not include its own antennas but instead utilizes and/or otherwiseshares one or more antennas (e.g., Wi-Fi antenna) of the wireless devicein which the wireless power receiver client is embedded. Moreover, insome embodiments, the wireless power receiver client may include asingle antenna that provides data transmission functionality as well aspower/data reception functionality. Additional components are alsopossible.

A combiner 455 receives and combines the received power transmissionsignals from the power transmitter in the event that the receiver 400has more than one antenna. The combiner can be any combiner or dividercircuit that is configured to achieve isolation between the output portswhile maintaining a matched condition. For example, the combiner 455 canbe a Wilkinson Power Divider circuit. The rectifier 450 receives thecombined power transmission signal from the combiner 455, if present,which is fed through the power meter 440 to the battery 420 forcharging. The power meter 440 can measure the received power signalstrength and provides the control logic 410 with this measurement.

The control logic 410 can receive the battery power level from thebattery 420 itself. The control logic 410 may also transmit/receive viathe communication block 430 a data signal on a data carrier frequency,such as the base signal clock for clock synchronization. The beaconsignal generator 460 generates the beacon signal, or calibration signal,transmits the beacon signal using either the antenna 480 or 490 afterthe beacon signal is encoded.

It may be noted that, although the battery 420 is shown as charged by,and providing power to, the receiver 400, the receiver may also receiveits power directly from the rectifier 450. This may be in addition tothe rectifier 450 providing charging current to the battery 420, or inlieu of providing charging. Also, it may be noted that the use ofmultiple antennas is one example of implementation and the structure maybe reduced to one shared antenna.

In some embodiments, the control logic 410 and/or the IoT control module425 can communicate with and/or otherwise derive IoT information fromthe device in which the wireless power receiver client 400 is embedded.Although not shown, in some embodiments, the wireless power receiverclient 400 can have one or more data connections (wired or wireless)with the device in which the wireless power receiver client 400 isembedded over which IoT information can be obtained. Alternatively, oradditionally, IoT information can be determined and/or inferred by thewireless power receiver client 400, e.g., via one or more sensors. Asdiscussed above, the IoT information can include, but is not limited to,information about the capabilities of the device in which the wirelesspower receiver client is embedded, usage information of the device inwhich the wireless power receiver client is embedded, power levels ofthe battery or batteries of the device in which the wireless powerreceiver client is embedded, and/or information obtained or inferred bythe device in which the wireless power receiver client is embedded orthe wireless power receiver client itself, e.g., via sensors, etc.

In some embodiments, a client identifier (ID) module 415 stores a clientID that can uniquely identify the power receiver client in a wirelesspower delivery environment. For example, the ID can be transmitted toone or more wireless power transmission systems when communication isestablished. In some embodiments, power receiver clients may also beable to receive and identify other power receiver clients in a wirelesspower delivery environment based on the client ID.

An optional motion sensor 495 can detect motion and signal the controllogic 410 to act accordingly. For example, a device receiving power mayintegrate motion detection mechanisms such as accelerometers orequivalent mechanisms to detect motion. Once the device detects that itis in motion, it may be assumed that it is being handled by a user, andwould trigger a signal to the array to either to stop transmittingpower, or to lower the power transmitted to the device. In someembodiments, when a device is used in a moving environment like a car,train or plane, the power might only be transmitted intermittently or ata reduced level unless the device is critically low on power.

FIGS. 5A and 5B depict diagrams illustrating an example multipathwireless power delivery environment 500, according to some embodiments.The multipath wireless power delivery environment 500 includes a useroperating a wireless device 502 including one or more wireless powerreceiver clients 503. The wireless device 502 and the one or morewireless power receiver clients 503 can be wireless device 102 of FIG. 1and wireless power receiver client 103 of FIG. 1 or wireless powerreceiver client 400 of FIG. 4, respectively, although alternativeconfigurations are possible. Likewise, wireless power transmissionsystem 501 can be wireless power transmission system 101 FIG. 1 orwireless power transmission system 300 of FIG. 3, although alternativeconfigurations are possible. The multipath wireless power deliveryenvironment 500 includes reflective objects 506 and various absorptiveobjects, e.g., users, or humans, furniture, etc.

Wireless device 502 includes one or more antennas (or transceivers) thathave a radiation and reception pattern 510 in three-dimensional spaceproximate to the wireless device 102. The one or more antennas (ortransceivers) can be wholly or partially included as part of thewireless device 102 and/or the wireless power receiver client (notshown). For example, in some embodiments one or more antennas, e.g.,Wi-Fi, Bluetooth, etc. of the wireless device 502 can be utilized and/orotherwise shared for wireless power reception. As shown in the exampleof FIGS. 5A and 5B, the radiation and reception pattern 510 comprises alobe pattern with a primary lobe and multiple side lobes. Other patternsare also possible.

The wireless device 502 transmits a beacon (or calibration) signal overmultiple paths to the wireless power transmission system 501. Asdiscussed herein, the wireless device 502 transmits the beacon in thedirection of the radiation and reception pattern 510 such that thestrength of the received beacon signal by the wireless powertransmission system, e.g., RSSI, depends on the radiation and receptionpattern 510. For example, beacon signals are not transmitted where thereare nulls in the radiation and reception pattern 510 and beacon signalsare the strongest at the peaks in the radiation and reception pattern510, e.g., peak of the primary lobe. As shown in the example of FIG. 5A,the wireless device 502 transmits beacon signals over five paths P1-P5.Paths P4 and P5 are blocked by reflective and/or absorptive object 506.The wireless power transmission system 501 receives beacon signals ofincreasing strengths via paths P1-P3. The bolder lines indicate strongersignals. In some embodiments the beacon signals are directionallytransmitted in this manner to, for example, avoid unnecessary RF energyexposure to the user.

A fundamental property of antennas is that the receiving pattern(sensitivity as a function of direction) of an antenna when used forreceiving is identical to the far-field radiation pattern of the antennawhen used for transmitting. This is a consequence of the reciprocitytheorem in electromagnetics. As shown in the example of FIGS. 5A and 5B,the radiation and reception pattern 510 is a three-dimensional lobeshape. However, the radiation and reception pattern 510 can be anynumber of shapes depending on the type or types, e.g., horn antennas,simple vertical antenna, etc. used in the antenna design. For example,the radiation and reception pattern 510 can comprise various directivepatterns. Any number of different antenna radiation and receptionpatterns are possible for each of multiple client devices in a wirelesspower delivery environment.

Referring again to FIG. 5A, the wireless power transmission system 501receives the beacon (or calibration) signal via multiple paths P1-P3 atmultiple antennas or transceivers. As shown, paths P2 and P3 are directline of sight paths while path P1 is a non-line of sight path. Once thebeacon (or calibration) signal is received by the wireless powertransmission system 501, the power transmission system 501 processes thebeacon (or calibration) signal to determine one or more receivecharacteristics of the beacon signal at each of the multiple antennas.For example, among other operations, the wireless power transmissionsystem 501 can measure the phases at which the beacon signal is receivedat each of the multiple antennas or transceivers.

The wireless power transmission system 501 processes the one or morereceive characteristics of the beacon signal at each of the multipleantennas to determine or measure one or more wireless power transmitcharacteristics for each of the multiple RF transceivers based on theone or more receive characteristics of the beacon (or calibration)signal as measured at the corresponding antenna or transceiver. By wayof example and not limitation, the wireless power transmitcharacteristics can include phase settings for each antenna ortransceiver, transmission power settings, etc.

As discussed herein, the wireless power transmission system 501determines the wireless power transmit characteristics such that, oncethe antennas or transceivers are configured, the multiple antennas ortransceivers are operable to transit a wireless power signal thatmatches the client radiation and reception pattern in thethree-dimensional space proximate to the client device. FIG. 5Billustrates the wireless power transmission system 501 transmittingwireless power via paths P1-P3 to the wireless device 502.Advantageously, as discussed herein, the wireless power signal matchesthe client radiation and reception pattern 510 in the three-dimensionalspace proximate to the client device. Said another way, the wirelesspower transmission system will transmit the wireless power signals inthe direction in which the wireless power receiver has maximum gain,e.g., will receive the most wireless power. As a result, no signals aresent in directions in which the wireless power receiver cannot receiver,e.g., nulls and blockages. In some embodiments, the wireless powertransmission system 501 measures the RSSI of the received beacon signaland if the beacon is less than a threshold value, the wireless powertransmission system will not send wireless power over that path.

The three paths shown in the example of FIGS. 5A and 5B are illustratedfor simplicity, it is appreciated that any number of paths can beutilized for transmitting power to the wireless device 502 depending on,among other factors, reflective and absorptive objects in the wirelesspower delivery environment.

II. Techniques for Reducing Messaging Requirements

In order to accurately generate wireless power delivery schedules, datais collected from devices within the wireless power deliveryenvironment. In general, the more information known regarding thedevices in the wireless power delivery environment, the more effectivethe wireless power delivery to those devices. The information collectedfrom the device can include, among other parameters, battery type, powerusage, device model, present charge level and amount of power deliveredper power cycle.

In order to convey this information to a wireless power transmissionsystem, the wireless power receiver client (or receiver) typicallycollects the information from a corresponding device, e.g., in which thewireless power receiver client is embedded, or attempts to infer theinformation if it is not available. The receiver then provides theinformation directly to the charger via a messaging protocol. Variousmessaging protocols can be utilized to convey the device information. Incurrent systems, the device information such as, for example, devicetype, model number, etc., is re-transmitted to the wireless powertransmission system every time the receiver reengages the wireless powertransmission system. As discussed herein, engagement or reengagementwith a wireless power transmission system constitutes a discovery event.The continual retransmission of device information on reengagement canbe burdensome on the receiver resulting in unnecessary energyconsumption and delay due to the excessive and unnecessarytransmissions. Accordingly, the techniques discussed herein minimizedata communication through the retention of the data within the wirelesspower transmission system, e.g., charger, or within a cloud-basedprocessing system.

FIG. 6 depicts a diagram illustrating an example wireless power deliveryenvironment 600, according to some embodiments. The example wirelesspower delivery environment 600 includes a wireless power transmissionsystem 601 and a device D1 initially located within wireless powerdelivery coverage area 615 the wireless power transmission system 601 attime t1, traversing along path M out of the wireless power deliverycoverage area 615 at time t2, and back into the wireless power deliverycoverage area 615 at time t3. The wireless power transmission system 601can be wireless power transmission system 101 of FIG. 1 or wirelesspower transmission system 300 of FIG. 3 although alternativeconfigurations are possible. As discussed herein, the device D1 can be,for example, a wireless device 102 of FIG. 1 including one or morewireless power receiver clients. Each wireless power receiver client canbe a wireless power receiver client 103 of FIG. 1 or a wireless powerreceiver client 400 of FIG. 4 although alternative configurations arepossible.

The wireless power transmission system 601 can, among other features,reduce unnecessary messaging in the wireless power delivery environment600 by generating, maintaining, and/or using a device registry. In someembodiments, the processing system 650 can, in whole or in part,alternatively or additionally, facilitate reduction in unnecessarymessaging in the wireless power delivery environment 600 by generatingand/or maintaining the device registry for one or more related orunrelated wireless power transmission systems. In some embodiments, thedevice registry can include a list of receiver identifiers andcorresponding device information. Accordingly, use of the deviceregistry can reduce data communication by retaining receiverinformation. As discussed, the device registry can be maintained withinthe wireless power transmission system 601 and/or within the cloud-basedprocessing system 650. An example device registry table is shown anddiscussed in greater detail with reference to FIG. 9.

In some embodiments, wireless power transmission systems can query acloud-based processing system 650 to obtain device information on adevice it has never ‘seen’, e.g., the device has never been within thecoverage area of the wireless power transmission system. Alternatively,or additionally, a cloud-based processing system 650 can request deviceinformation from wireless power transmission system, update one or moreglobal device registries, and push out device registry updates towireless power transmission systems. It is appreciated that all deviceinformation may not be pushed out to all wireless power transmissionsystems. For example, a national coffee chain might push out a deviceregistry update including device information for a particular deviceonly to stores within one or more particular regions proximate to priorusage of the device.

It is appreciated that some or all of the functionality of theprocessing system 650 can alternatively or additionally be provided bythe wireless power transmission system 601 or another local (non-cloudbased) processing system (not shown). As shown, the processing system650 includes multiple servers 640 and data repositories 630. Any numberof servers 640 and/or data repositories 630 may be included inprocessing system 650. As shown in the example of FIG. 6, the processingsystem 650 can be a cloud-based or central processing system; however,it is appreciated that in some embodiments, the processing system 650can be a local processing system, e.g., co-located with or near thewireless power transmission system(s) in the wireless power deliveryenvironment or coverage area 615 or built into and/or otherwise combinedwith a wireless power transmission system.

The network 660 can be any collection of distinct networks operatingwholly or partially in conjunction to provide connectivity and mayappear as one or more networks to the serviced systems and devices. Forexample, network 660 can be, an open network, such as the Internet, aprivate network, such as an intranet and/or the extranet, and/orcombinations or variations thereof. The device, wireless powertransmission system and the registration system may each access network660 by different access networks (not shown) which are shown includedwithin network 660.

To further illustrate the operation of the wireless power transmissionsystem 601, example device D1, and the processing system 650, the FIG. 7provided. FIG. 7 depicts a sequence diagram 700 illustrating exampleoperations for reducing messaging in a wireless power deliveryenvironment, according to some embodiments. In the example of FIG. 7,device D1 includes a single (embedded) wireless power receiver client(WPRC). As discussed herein, it is appreciated that at device caninclude and/or otherwise be associated with multiple wireless powerreceiver clients.

To begin, communications are established between the wireless powerreceiver client and wireless power transmission system 601. Next, thewireless power receiver client transmits its receiver identifier (ID) tothe wireless power transmission system 601. As discussed herein, eachwireless power receiver client can include a receiver ID, e.g., radioID, that may be transmitted at the initial data exchange between thewireless power transmission system and the wireless power receiverclient. The wireless power transmission system processes the receiver IDto determine whether it is known. For example, a known receiver ID willhave an entry in a device registry.

As discussed herein, the device registry can be maintained by a wirelesspower transmission system and/or a cloud-based processing system. Insome embodiments, the wireless power transmission system 601 makes adetermination as to whether the receiver is known by checking if thereceiver ID is included in a local device registry. In some embodiments,the wireless power transmission system 601 can alternatively oradditionally query processing system 650 to determine if the receiver IDis included in a cloud-based device registry. As discussed herein, thedevice registry can be maintained in whole or in part by a wirelesspower transmission system and/or a processing system.

In some instances, the device registry is maintained by the cloud-basedprocessing system. In such cases, updates to the device registry can beperiodically pushed out to wireless power transmission systems.Alternatively, or additionally, and as shown in the example of FIG. 7,wireless power transmission systems can query a cloud-based deviceregistry to determine if the device is known. As discussed herein, if adevice is recognized or known, the device can forego sending deviceinformation to the wireless power transmission system—even the firsttime the device is discovered by a particular wireless powertransmission system when that wireless power transmission system is partof a larger network. For example, a national coffee chain could identifythe device in one store and later recognize that same device in anotherstore.

As shown in the example of FIG. 7, the receiver is initially unknown ornot recognized by the wireless power. Accordingly, the wireless powertransmission system requests device information from the wireless powerreceiver which, in turn, requests the information from the deviceitself. Some or all of the device information could also be discoverableor inferred by the wireless power receiver client. For example, thepower amount received per power cycle is readily ascertained. Identicalreceivers may vary considerably in the average amount of power collectedper power cycle based upon the environment, distance from the charger,orientation, and other factors. As such, knowledge of the average powerreceived, as well as any patterns of power collection (such as a phoneplaced near the charger at certain hours but not others) is valuableinformation. Other collected data includes current power levels,location information, actual instant power being received, etc.

Once the device information is obtained, the wireless power receiverclient sends the device information to wireless power transmissionsystem 601. Wireless power transmission system 601 then associates thereceiver ID with the device information and stores the associated datain the device registry. Again, the device registry may be, in whole orin part, maintained on processing system 650. Next, wireless powertransmission system 601 generates and/or updates beacon and/or wirelesspower transmission schedules and provides this information to thewireless power receiver clients. The wireless power receiver clientssend beacon signals during their beacon schedules and receive powerduring their associated power schedules.

At time t2, device D1 leaves the wireless power coverage area or regionand, thus, is no longer able to receive wireless power from wirelesspower transmission system 601. Although not shown, the wireless powertransmission system 601 can adjust the beacon and power schedules toremove device D1 from the schedule. At a later time t3, device D1returns to the wireless power coverage area or region. The wirelesspower transmission system discovers the new device and communicationsare established between the wireless power receiver client and wirelesspower transmission system 601. Next, the wireless power receiver clienttransmits its receiver identifier (ID) to the wireless powertransmission system 601.

The wireless power transmission system processes the receiver ID todetermine whether it is known. For example, a known receiver ID willhave an entry in a device registry. Again, the wireless powertransmission system 601 can work alone or in conjunction with theprocessing system 650 to determine if the receiver ID is known. In thisexample, the device D1 is clearly known from previous interactions.Accordingly, the wireless power transmission system does not requestdevice information and instead accesses the device information from thedevice registry using the receiver ID. Lastly, wireless powertransmission system 601 generates and/or updates beacon and/or wirelesspower transmission schedules and provides this information to thewireless power receiver clients. The wireless power receiver clientssend beacon signals during their beacon schedules and receive powerduring their associated power schedules.

FIG. 8 depicts a flow diagram illustrating an example process 800 forreducing unnecessary messaging in a wireless power delivery environment,according to some embodiments. A wireless power transmission system suchas, for example, wireless power transmission system 601 of FIG. 6 orwireless power transmission system 101 of FIG. 1 can, among otherfunctions, perform example process 800. Alternatively, or additionally,example process 800 can be performed, in whole or in part, by acloud-based process system 650.

To begin, at 810, the wireless power transmission system providesretrodirective wireless power to the wireless power receiver clientswithin the coverage area according to a wireless power delivery scheduleand location as determined by beacon signals received from the wirelesspower receiver client. At decision 812, the wireless power transmissionsystem determines if a discovery event has occurred. As discussedherein, engagement or reengagement by a device or wireless powerreceiver with wireless power transmission system constitutes a discoveryevent. For example, a discovery event occurs if a device is turned ‘ON’within range of a wireless power transmitter, is brought from outside ofrange to within range of the wireless power transmission system, etc.

If a discovery event occurs for a particular wireless power receiver, at814, the wireless power transmission system processes the receiveridentifier (ID) to determine if the receiver is known. As discussedherein, the receiver ID uniquely identifies the wireless power receiverclient associated with a device. For example, a known receiver ID willhave an entry in a device registry. At decision 816, if the wirelesspower transmission system determines that the device is unknown then, at818, the wireless power transmission system processes received deviceinformation. Next at 820, the wireless power transmission systemassociates the receiver ID with the device information and, at 822,stores the associated information in a device registry as discussedherein.

Lastly, at 824, the wireless power transmission system updates thebeacon and/or wireless power transmission schedules and returns to step810, providing wireless power according to the wireless powertransmission schedule.

FIG. 9 depicts an example device registry table 900, according to someembodiments. More specifically, the example device registry table 900includes various receiver identifiers with the associated deviceinformation. As discussed herein, a device registry can be maintained bya wireless power transmission system and/or a cloud-based processingsystem. Alternatively, multiple device registries can be maintained. Forexample, a local device registry can be maintained by the wireless powertransmission system and a central or global device registry can bemaintained by a cloud-based processing system. In such instances, thelocal device registry can comprise a subset of the global deviceregistry.

FIG. 10 depicts a block diagram illustrating example components of arepresentative mobile device or tablet computer 1000 with a wirelesspower receiver or client in the form of a mobile (or smart) phone ortablet computer device, according to an embodiment. Various interfacesand modules are shown with reference to FIG. 10, however, the mobiledevice or tablet computer does not require all of modules or functionsfor performing the functionality described herein. It is appreciatedthat, in many embodiments, various components are not included and/ornecessary for operation of the category controller. For example,components such as GPS radios, cellular radios, and accelerometers maynot be included in the controllers to reduce costs and/or complexity.Additionally, components such as ZigBee™ radios and RFID transceivers,along with antennas, can populate the Printed Circuit Board.

The wireless power receiver client can be a power receiver client 103 ofFIG. 1, although alternative configurations are possible. Additionally,the wireless power receiver client can include one or more RF antennasfor reception of power and/or data signals from a power transmissionsystem, e.g., wireless power transmission system 101 of FIG. 1.

FIG. 11 depicts a diagrammatic representation of a machine, in theexample form, of a computer system within which a set of instructions,for causing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

In the example of FIG. 11, the computer system includes a processor,memory, non-volatile memory, and an interface device. Various commoncomponents (e.g., cache memory) are omitted for illustrative simplicity.The computer system 1100 is intended to illustrate a hardware device onwhich any of the components depicted in the example of FIG. 1 (and anyother components described in this specification) can be implemented.For example, the computer system can be any radiating object or antennaarray system. The computer system can be of any applicable known orconvenient type. The components of the computer system can be coupledtogether via a bus or through some other known or convenient device.

The processor may be, for example, a conventional microprocessor such asan Intel Pentium microprocessor or Motorola power PC microprocessor. Oneof skill in the relevant art will recognize that the terms“machine-readable (storage) medium” or “computer-readable (storage)medium” include any type of device that is accessible by the processor.

The memory is coupled to the processor by, for example, a bus. Thememory can include, by way of example but not limitation, random accessmemory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM). Thememory can be local, remote, or distributed.

The bus also couples the processor to the non-volatile memory and driveunit. The non-volatile memory is often a magnetic floppy or hard disk, amagnetic-optical disk, an optical disk, a read-only memory (ROM), suchas a CD-ROM, EPROM, or EEPROM, a magnetic or optical card, or anotherform of storage for large amounts of data. Some of this data is oftenwritten, by a direct memory access process, into memory during executionof software in the computer 1100. The non-volatile storage can be local,remote, or distributed. The non-volatile memory is optional becausesystems can be created with all applicable data available in memory. Atypical computer system will usually include at least a processor,memory, and a device (e.g., a bus) coupling the memory to the processor.

Software is typically stored in the non-volatile memory and/or the driveunit. Indeed, for large programs, it may not even be possible to storethe entire program in the memory. Nevertheless, it should be understoodthat for software to run, if necessary, it is moved to a computerreadable location appropriate for processing, and for illustrativepurposes, that location is referred to as the memory in this paper. Evenwhen software is moved to the memory for execution, the processor willtypically make use of hardware registers to store values associated withthe software, and local cache that, ideally, serves to speed upexecution. As used herein, a software program is assumed to be stored atany known or convenient location (from non-volatile storage to hardwareregisters) when the software program is referred to as “implemented in acomputer-readable medium”. A processor is considered to be “configuredto execute a program” when at least one value associated with theprogram is stored in a register readable by the processor.

The bus also couples the processor to the network interface device. Theinterface can include one or more of a modem or network interface. Itwill be appreciated that a modem or network interface can be consideredto be part of the computer system. The interface can include an analogmodem, isdn modem, cable modem, token ring interface, satellitetransmission interface (e.g. “direct PC”), or other interfaces forcoupling a computer system to other computer systems. The interface caninclude one or more input and/or output devices. The I/O devices caninclude, by way of example but not limitation, a keyboard, a mouse orother pointing device, disk drives, printers, a scanner, and other inputand/or output devices, including a display device. The display devicecan include, by way of example but not limitation, a cathode ray tube(CRT), liquid crystal display (LCD), or some other applicable known orconvenient display device. For simplicity, it is assumed thatcontrollers of any devices not depicted in the example of FIG. 11 residein the interface.

In operation, the computer system 1100 can be controlled by operatingsystem software that includes a file management system, such as a diskoperating system. One example of operating system software withassociated file management system software is the family of operatingsystems known as Windows® from Microsoft Corporation of Redmond, Wash.,and their associated file management systems. Another example ofoperating system software with its associated file management systemsoftware is the Linux operating system and its associated filemanagement system. The file management system is typically stored in thenon-volatile memory and/or drive unit and causes the processor toexecute the various acts required by the operating system to input andoutput data and to store data in the memory, including storing files onthe non-volatile memory and/or drive unit.

Some portions of the detailed description may be presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “processing” or “computing” or“calculating” or “determining” or “displaying” or the like, refer to theaction and processes of a computer system, or similar electroniccomputing device, that manipulates and transforms data represented asphysical (electronic) quantities within the computer system's registersand memories into other data similarly represented as physicalquantities within the computer system memories or registers or othersuch information storage, transmission or display devices.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the methods of some embodiments. The requiredstructure for a variety of these systems will appear from thedescription below. In addition, the techniques are not described withreference to any particular programming language, and variousembodiments may thus be implemented using a variety of programminglanguages.

In alternative embodiments, the machine operates as a standalone deviceor may be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in a client-server network environment or as a peermachine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personalcomputer (PC), a tablet PC, a laptop computer, a set-top box (STB), apersonal digital assistant (PDA), a cellular telephone, an iPhone, aBlackberry, a processor, a telephone, a web appliance, a network router,switch or bridge, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine.

While the machine-readable medium or machine-readable storage medium isshown in an exemplary embodiment to be a single medium, the term“machine-readable medium” and “machine-readable storage medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-readable medium” and “machine-readable storage medium” shallalso be taken to include any medium that is capable of storing, encodingor carrying a set of instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies of thepresently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of thedisclosure, may be implemented as part of an operating system or aspecific application, component, program, object, module or sequence ofinstructions referred to as “computer programs.” The computer programstypically comprise one or more instructions set at various times invarious memory and storage devices in a computer, and that, when readand executed by one or more processing units or processors in acomputer, cause the computer to perform operations to execute elementsinvolving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fullyfunctioning computers and computer systems, those skilled in the artwill appreciate that the various embodiments are capable of beingdistributed as a program product in a variety of forms, and that thedisclosure applies equally regardless of the particular type of machineor computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readablemedia, or computer-readable (storage) media include but are not limitedto recordable type media such as volatile and non-volatile memorydevices, floppy and other removable disks, hard disk drives, opticaldisks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital VersatileDisks, (DVDs), etc.), among others, and transmission type media such asdigital and analog communication links.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof, means any connection or coupling,either direct or indirect, between two or more elements; the coupling ofconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import, when used in this application, shall referto this application as a whole and not to any particular portions ofthis application. Where the context permits, words in the above DetailedDescription using the singular or plural number may also include theplural or singular number respectively. The word “or,” in reference to alist of two or more items, covers all of the following interpretationsof the word: any of the items in the list, all of the items in the list,and any combination of the items in the list.

The above detailed description of embodiments of the disclosure is notintended to be exhaustive or to limit the teachings to the precise formdisclosed above. While specific embodiments of, and examples for, thedisclosure are described above for illustrative purposes, variousequivalent modifications are possible within the scope of thedisclosure, as those skilled in the relevant art will recognize. Forexample, while processes or blocks are presented in a given order,alternative embodiments may perform routines having steps, or employsystems having blocks, in a different order, and some processes orblocks may be deleted, moved, added, subdivided, combined, and/ormodified to provide alternative or subcombinations. Each of theseprocesses or blocks may be implemented in a variety of different ways.Also, while processes or blocks are, at times, shown as being performedin a series, these processes or blocks may instead be performed inparallel, or may be performed at different times. Further, any specificnumbers noted herein are only examples: alternative implementations mayemploy differing values or ranges.

The teachings of the disclosure provided herein can be applied to othersystems, not necessarily the system described above. The elements andacts of the various embodiments described above can be combined toprovide further embodiments.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the disclosure can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further embodiments of thedisclosure.

These and other changes can be made to the disclosure in light of theabove Detailed Description. While the above description describescertain embodiments of the disclosure, and describes the best modecontemplated, no matter how detailed the above appears in text, theteachings can be practiced in many ways. Details of the system may varyconsiderably in its implementation details, while still beingencompassed by the subject matter disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the disclosure should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the disclosure with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the disclosure to the specific embodimentsdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe disclosure encompasses not only the disclosed embodiments, but alsoall equivalent ways of practicing or implementing the disclosure underthe claims.

While certain aspects of the disclosure are presented below in certainclaim forms, the inventors contemplate the various aspects of thedisclosure in any number of claim forms. For example, while only oneaspect of the disclosure is recited as a means-plus-function claim under35 U.S.C. § 112,

6, other aspects may likewise be embodied as a means-plus-functionclaim, or in other forms, such as being embodied in a computer-readablemedium. (Any claims intended to be treated under 35 U.S.C. § 112,

6 will begin with the words “means for”.) Accordingly, the applicantreserves the right to add additional claims after filing the applicationto pursue such additional claim forms for other aspects of thedisclosure.

The detailed description provided herein may be applied to othersystems, not necessarily only the system described above. The elementsand acts of the various examples described above can be combined toprovide further implementations of the invention. Some alternativeimplementations of the invention may include not only additionalelements to those implementations noted above, but also may includefewer elements. These and other changes can be made to the invention inlight of the above Detailed Description. While the above descriptiondefines certain examples of the invention, and describes the best modecontemplated, no matter how detailed the above appears in text, theinvention can be practiced in many ways. Details of the system may varyconsiderably in its specific implementation, while still beingencompassed by the invention disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the invention should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the invention with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the invention to the specific examplesdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe invention encompasses not only the disclosed examples, but also allequivalent ways of practicing or implementing the invention.

What is claimed is:
 1. A method of reducing messaging in a wirelesspower delivery environment, the method comprising: responsive to a firstdiscovery event, receiving, by a wireless power transmission system, afirst communication including a receiver identifier (ID) that uniquelyidentifies a first wireless power receiver client associated with afirst device in the wireless power delivery environment; receivingdevice information corresponding to the first device; associating thereceiver ID with device information corresponding to the first device;responsive to a subsequent discovery event, receiving a secondcommunication including the receiver ID that uniquely identifies thefirst wireless power receiver client associated with the first device inthe wireless power delivery environment; and retrieving the deviceinformation corresponding to the first device from a device registryusing the receiver ID.
 2. The method of claim 1, further comprising:responsive to associating the receiver ID with device informationcorresponding to the first device, storing the associated receiver IDwith the device information in the device registry.
 3. The method ofclaim 2, wherein the device registry is stored on the wireless powertransmission system.
 4. The method of claim 2, wherein the deviceregistry is stored on a cloud-based processing system.
 5. The method ofclaim 1, further comprising: prior to receiving the device informationcorresponding to the first device, processing the receiver ID todetermine if the first device is a known device; and sending a requestfor the device information for delivery to the first power receiverclient when the first device is a known device.
 6. The method of claim1, further comprising: generating a wireless power delivery schedule forthe wireless power transmission system, wherein the wireless powerdelivery schedule includes the first wireless power receiver client. 7.The method of claim 1, wherein a discovery event comprises an indicationthat the first device is available for receiving wireless power withinthe wireless power delivery environment.
 8. The method of claim 1,wherein the receiver ID comprises a radio ID.
 9. The method of claim 8,wherein the radio ID is associated with a model number.
 10. The methodof claim 9, wherein the model number indicates one or more of a batterycapacity or a device type of the first device.
 11. A method of reducingmessaging in a wireless power delivery environment, the methodcomprising: responsive to a first discovery event, processing a firstcommunication including a receiver identifier (ID) that uniquelyidentifies a first wireless power receiver client associated with afirst device in the wireless power delivery environment; receivingdevice information corresponding to the first device; associating thereceiver ID with device information corresponding to the first device;and storing the associated receiver ID with the device information in adevice registry.
 12. The method of claim 11, further comprising:responsive to a subsequent discovery event, receiving the receiver IDthat uniquely identifies the first wireless power receiver clientassociated with the first device in the wireless power deliveryenvironment; and retrieving the device information corresponding to thefirst device from the device registry using the receiver ID.
 13. Themethod of claim 11, further comprising: responsive to associating thereceiver ID with device information corresponding to the first device,storing the associated receiver ID with the device information in thedevice registry.
 14. The method of claim 13, wherein the device registryis stored, in whole or in part, on the wireless power transmissionsystem and on a cloud-based processing system.
 15. The method of claim11, further comprising: prior to receiving the device informationcorresponding to the first device, processing the receiver ID todetermine if the first device is a known device; and sending a requestfor the device information for delivery to the first power receiverclient when the first device is a known device.
 16. The method of claim15, further comprising querying a cloud-based processing system todetermine if the first device is a known device.
 17. The method of claim11, further comprising: generating a wireless power delivery schedulefor the wireless power transmission system, wherein the wireless powerdelivery schedule includes the first wireless power receiver client. 18.The method of claim 11, wherein the receiver ID comprises a radio ID,wherein the radio ID is associated with a model number that indicatesone or more of a battery capacity or a device type of the first device.19. A wireless power transmission system, comprising: anadaptively-phased antenna array having multiple radio frequency (RF)transceivers; control circuitry configured to: responsive to a firstdiscovery event, process a first received communication including areceiver identifier (ID) that uniquely identifies a first wireless powerreceiver client associated with a first device in the wireless powerdelivery environment; process device information corresponding to thefirst device; associate the receiver ID with device informationcorresponding to the first device; responsive to a subsequent discoveryevent, process a second communication including the receiver ID thatuniquely identifies the first wireless power receiver client associatedwith the first device in the wireless power delivery environment; andretrieve the device information corresponding to the first device from adevice registry using the receiver ID.
 20. The wireless powertransmission system of claim 19, wherein the control circuity is furtherconfigured to: responsive to associating the receiver ID with deviceinformation corresponding to the first device, store the associatedreceiver ID with the device information in the device registry.